HPXMLtoOpenStudio/resources/hvac.rb:5310

• The unit-multiplier scaling for crankcase_heater_watts was removed for both cooling systems and heat pumps, but crankcase heater power is still used to drive EMS “OtherEquipment” power (hvac_system.crankcase_heater_watts). This will under-scale crankcase heater energy in multifamily/unit-multiplier runs. Add back scaling of *_sys.crankcase_heater_watts here (or alternatively, scale inside apply_crankcase_heater_ems_program using number_of_units/unit multiplier) so results remain consistent with other HVAC power terms.

  def self.apply_unit_multiplier(hpxml_bldg, hpxml_header)

HPXMLtoOpenStudio/resources/hvac.rb:4990

• apply_defrost_ems_program now assumes an outdoor drybulb EMS sensor already exists (and is tagged via additionalProperties), but it doesn’t create the sensor or validate that tout_db_sensor was found before later using it. This creates a hidden coupling to the call site and can fail at runtime if the sensor wasn’t created (e.g., if the function is reused from another code path). Consider either (a) creating the sensor here when not found, or (b) raising a clear error if tout_db_sensor is nil with guidance on the required setup.

    )

    # Sensors
    tout_db_sensor = model.getEnergyManagementSystemSensors.find { |s| s.additionalProperties.getFeatureAsString('ObjectType').to_s == Constants::ObjectTypeOATDrybulbSensor }

    htg_coil_rtf_sensor = Model.add_ems_sensor(
      model,
      name: "#{htg_coil.name} rtf s",
      output_var_or_meter_name: 'Heating Coil Runtime Fraction',
      key_name: htg_coil.name
    )